Previewing video data in a video communication environment

ABSTRACT

In one example implementation, a request from a first endpoint is identified for a second endpoint to join a video communication session. Particular video data captured at the first endpoint is displayed at the second endpoint prior to the second endpoint joining the video communication session. In certain embodiments, the particular video data captured at the first endpoint can be displayed at the second endpoint without the user of the first endpoint being made aware that the particular video data was displayed at the second endpoint.

TECHNICAL FIELD

This disclosure relates in general to the field of communications and,more particularly, to establishing communication sessions within a videoconference environment.

BACKGROUND

Video services have become increasingly important in today's society. Incertain architectures, service providers may seek to offer sophisticatedvideoconferencing services for their end users. The videoconferencingarchitecture can offer an “in-person” meeting experience over a network.Videoconferencing architectures can deliver real-time, face-to-faceinteractions between people using advanced visual, audio, andcollaboration technologies. In addition to videoconferencing, videocommunications have been expanding into consumer markets, with serviceproviders providing video chat and other personal video conferencing andcommunication applications, allowing users to engage in a telephonicconversation that includes both an audio and visual components, allowingthe participants to both hear and see the other caller during thecommunication session.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a simplified schematic diagram of a communication system forfacilitating a video communication session in accordance with oneembodiment;

FIG. 2A is a simplified block diagram of a first example communicationsystem enabling video previewing within a conferencing environment inaccordance with one embodiment of the present disclosure;

FIG. 2B is a simplified block diagram of a second example communicationsystem enabling video previewing within a conferencing environment inaccordance with another embodiment of the present disclosure;

FIGS. 3A-3B illustrate representations of example attempts to initiatevideo communication sessions in accordance with at least someembodiments of the present disclosure; and

FIGS. 4A-4B are simplified flowcharts illustrating example operationsassociated with at least some embodiments of the communication system.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

Overview

An example method may include identifying a request from a firstendpoint, for a second endpoint to join a video communication session.Particular video data captured at the first endpoint can be displayed atthe second endpoint prior to the second endpoint joining the videocommunication session. In another implementation, a system may include aprocessor, a memory element, and a video communication previewer. Thevideo communication previewer can be configured to identify a requestfrom a first endpoint, for a second endpoint to join a videocommunication session, where each of the first and second endpoints areconfigured to receive and send video data within the video communicationsession, and allow particular video data captured at the first endpointto be displayed at the second endpoint prior to the second endpointjoining the video communication session.

These and other embodiments can each optionally include one or more ofthe following features. A confirmation from the second endpoint to jointhe video communication session can be identified following a display ofthe particular video data on the second endpoint. The particular videodata can be displayed as video data on the second endpoint. Theparticular video data can be displayed on the second endpoint as a stillimage. It can be identified that the particular video data includespresentation of a human face before allowing the particular video datato be presented on the second endpoint. A presentation of a human facein the particular video data can be identified. Face data correspondingto the presented human face can be associated with a video caller usingthe first endpoint.

Furthermore, a response can be identified (received at the secondendpoint) indicating whether a video communication session with thevideo caller is desired. It can be identified that a second request tojoin a second video communication session includes the video callerbased on a facial recognition of preliminary video data (e.g., capturedduring initiation of the second request), the facial recognitionincluding a comparison of at least a portion of the preliminary videodata with the face data.

Further, embodiments can each optionally include one or more of thefollowing additional features. A denial from the second endpoint can beidentified declining to join the video communication session following adisplay of the particular video data on the second endpoint, where thesecond endpoint does not join the video communication session. Aresponse from the second endpoint can be identified indicating whether avideo communication session with first endpoint is desired. An actioncan be performed corresponding to the second request based on theresponse. The action can include associating the identified responsewith an identifier corresponding to the first endpoint. The action caninclude at least one of blocking the second request, causing an endpointother than the endpoint associated with the identifier to join thesecond video communication session, presenting a notification that thesecond request is associated with the identifier, reporting the secondrequest, joining the second video communication as an audio participantonly, and joining the second video communication session anonymouslywithout sharing video data within the session.

In addition, it can be identified that a second request to join a secondvideo communication session includes an endpoint associated with theidentifier and a response to the second request can be generated basedon the identified previous response associated with the identifier. Thefirst endpoint may not be made aware that the particular video data isdisplayed at the second endpoint prior to the second endpoint joiningthe video communication session. Identifying the request from the firstendpoint and allowing the particular video data to be displayed at thesecond endpoint can be performed by a video call server used toestablish video communication sessions between the second endpoint andat least one other endpoint. A video call server can include the videocommunication previewer. An endpoint can include at least a portion ofthe video communication previewer. The request from the first endpointcan be identified by the second endpoint and the second endpoint canallow the particular video data to be displayed at the second endpointprior to the second endpoint joining the video communication session.

Some or all of the features may be computer-implemented methods orfurther included in respective systems or other devices for performingthis described functionality. The details of these and other features,aspects, and implementations of the present disclosure are set forth inthe accompanying drawings and the description below. Other features,objects, and advantages of the disclosure will be apparent from thedescription and drawings, and from the claims.

Example Embodiments

FIG. 1 illustrates a simplified schematic diagram illustrating anexample communication system 100 for conducting a video communicationsession or video call with two or more participants in accordance withone example embodiment. In some implementations, communication system100 can additionally be configured to allow one or more participants topreview video call data captured of one or more other participants inthe video communication session before joining the video communicationsession themselves. Video data can, in some instances, include bothgraphical, photographic, and other data elements presented as videowithin the communication session. Audio data can also be captured andpresented within the video communication session. Video call data, asused herein, can refer to video data used within the video communicationsession, as well as, in some instances, both the video data andcorresponding audio data captured, presented, and shared within a videocommunication session.

FIG. 1 illustrates two or more video-enabled terminals 105, 110 (whichare representative of a type of endpoint) that can be utilized byparticipants 115, 120 in a video communication session (whichencompasses any type of video data transmission between two endpoints).A video communication server 125 can be utilized in connection with thevideo communication session. Indeed, terminals 105, 110 cancommunicatively couple to the video communication server 125 and thevideo communication session can be facilitated over the videocommunication server 125. Further, in some implementations,functionality permitting terminals to locate or otherwise identify otherterminals for a video call, functionality controlling the initiation andtermination of a session, functionality permitting previewing of videocall data by at least one of the participants, and other functionalitycan be provided using video communication server 125. Terminals 105, 110participating in or attempting to participate in a video call sessionserved by video communication server 125, can communicate with videocommunication server 125 over one or more networks 130.

Terminals 105, 110 configured for participation in a video communicationsession, such as a video conference, video call, or other communication,can include devices, software, and other logic and functionalitypermitting the terminal to capture and display video data for sharingwithin video communication sessions. For instance, each terminal 105,110 can include one or more camera devices (e.g., 135, 140) forcapturing video data in connection with a video communication session.The resolution, frame rate, and video format capable of being capturedby the camera devices 135, 140 can vary consistent with the mode andspecifications of the terminal and/or video communication service used.In some instances, video data captured by the camera can be converted(for instance, by video communication server 125 or the terminal itself)from a native or first format to another format more amenable for usewithin a particular video communication session. Such cameras can beintegrated into the terminal, be connected to the terminal as aperipheral device, or be otherwise associated with the terminal.

Further, terminals 105, 110 can also include video display devices(e.g., 145, 150), such as a monitor, television, screen, Telepresence™system display, or any other element capable of rendering video data forpresentation to human users during a video conference. In someinstances, video communication sessions can also permit the sharing ofvideo data, or synchronization with a corresponding audio or telephoniccommunication session, allowing users to exchange both video and audiodata and thereby communicate verbally and through non-verbal physicalcues (e.g., facial expressions) with other video session participants.In accordance with such implementations, terminal devices 105, 110 canfurther include microphone devices for capturing audio data from thehuman participant as well as speaker devices for presenting audio datacaptured from other participants in the communication session.

In some instances, combinations of video display devices (e.g., 145,150), camera devices (e.g., 135, 140), and other components, such asmicrophones, speakers, network interfaces, software modules, etc. usedto join and participate in video communication sessions can beintegrated within a single video communication terminal device together,such as a personal, laptop, or tablet computer, smartphone,Telepresence™ systems, etc. with integrated display device, microphone,camera, etc. In some instances, some of the devices used at the terminalin connection with a video communication session can be external orperipheral to other devices used by the terminal, such as a camera ormicrophone peripheral, external monitor (such as a television), amongother examples. In each instance, a terminal can allow for the capture,presentation, and communication of video call data within a videocommunication session.

The components of communication system 100 may use specializedapplications and hardware to create a system that can leverage anetwork. For instance, communication system 100 can use Internetprotocol (IP) technology and can run on an integrated voice, video, anddata network. In some instances, communication system 100 can leverageIP technology while providing data security and privacy through the useof virtual network connections between components of communicationsystem 100. The system can also support high quality, real-time voice,and video communications using broadband connections. It can furtheroffer capabilities for ensuring quality of service (QoS), security,reliability, and high availability for high-bandwidth videocommunication session connections.

As a general proposition, the video communication technology ofcommunication system 100 can be configured to simulate an in-personmeeting experience for its participants. In some settings, videocommunication technology can be used within business or governmentalsettings to facilitate a meeting over a video conference. Participantsin such meetings may be acting primarily as representatives of theirrespective companies, within an office setting, and may be lessconcerned with the potential for invasions of personal privacy withinsuch business-oriented conferences. As multi-party video communicationsexpand into the private domain however, it is anticipated that users maytend to be more concerned with and guarded against intrusions orviolations of their personal space during video calls. Unlike audiotelephone conversations, a video call can potentially display, to theother participants on the call, the participant's face, clothing,location, and surroundings, including background images of the caller'shome, children, pets, and possessions. While visual exposure of suchpersonal characteristics to others may be tolerated or even desired whenthe caller is participating in a video call with friends, family, orother participants with which the caller has a trusted relationship,such exposure can be very undesirable, and even threatening, if thecaller does not trust or wishes to avoid video calls with otherparticular or unknown callers.

Further, as video calling increases in popularity and deployment, it maybe anticipated that various abuses and unwelcome uses of video willemerge, such as video-based telemarketing, video stalking, video prankcalling, etc. In some instances, a user may wish to avoid or prepare forcertain video calls. For instance, a video call participant, in additionto worrying about how their voice sounds over the call, may also worryabout their physical appearance within the video call. For instance, aparticipant may feel comfortable participating in video calls with closefriends and family while casually dressed, but desire to be moreformally attired for video calls with others. Further, in certaininstances, a participant receiving a video call (or being invited tojoin a video communication session) can desire to screen the source ofan incoming call or video communication request. In some instances, auser can be presented with a name, telephone number, or other identifierin connection with a particular incoming video call or videocommunication invitation. Such identifiers, however, can be readilyforged, manipulated, and falsified using existing technology tomisrepresent the true source of an incoming call, making potential videocall participants susceptible to nefarious, misleading, and otherundesired virtual communication sessions.

In accordance with the teachings of the present disclosure,communication system 100 can be configured to overcome theseshortcomings (and others) in providing a visual preview of otherpotential participants in a video communication session. For instance,after a first participant in a video call, or other video communicationsession, has initiated the call and attempted to have anotherparticipant join the call, video images can be captured and sent fromthe calling terminal for viewing on the called or invited terminal toallow users of the called terminal to visually identify the caller.

Further, such preview images can be presented to the called user beforethe called terminal formally joins the session and begins transmittingvideo data of its own to the calling terminal and other terminalspotentially already participating in the video communication session. Insuch instances, the called user can peek into the video communicationsession to assess whether the called user would like to or feels safejoining the call, all while withholding video data of the called userfrom the other potential participants. Further, the called user can viewsuch preview video data without the caller being notified that thecalled user is screening the video call and viewing video data capturedfrom the caller(s).

For instance, the terminal receiving the call can present a ring tone tothe user indicating an incoming video call. Before the call is answered,the user can select to perform a peek to capture and view preview imagesof the caller. The receiving system can present the incoming video withno indication of the preview on the calling terminal's side. If the userdecides to answer the call, the terminal receiving the call can fullyjoin the communication session to begin transmitting video call data toother participants on the call.

Turning to FIGS. 2A-2B, simplified block diagrams 200 a, 200 b are shownillustrating possible details associated with communication system 100.In each of the examples of FIGS. 2A and 2B, example communicationsystems are shown including video communication terminal endpoints 105a-b, 108 a-b, 110 a-b configured to participate in video communicationsessions offered using video communication servers 125 a, 128 a. Eachterminal endpoint 105 a-b, 108 a-b, 110 a-b can include one or moreprocessors (e.g., 132 a, 132 b, 132 c) and one or more memory elements(144 a, 144 b, 144 c). Further, terminals 105 a-b, 108 a-b, 110 a-b canfurther include various other components and software-based modules foruse in connecting to and facilitating participation in a videocommunication session. For instance, terminals 105 a-b, 108 a-b, 110 a-bcan further include a respective video preview module 134 a, 134 b, 134c, respective network interfaces 146 a, 146 b, 146 c, respectivetransmitting modules 148 a, 148 b, 148 c, and respective receivingmodules 142 a, 142 b, 142 c. Additional modules and components can alsobe included, and modules and components shown and/or described can becombined and consolidated or divided into fewer or more componentsrespectively.

In general, terminals 105 a-b, 108 a-b, 110 a-b can include networkinterfaces 146 a, 146 b, 146 c configured for use in connecting theterminals 105 a-b, 108 a-b, 110 a-b to one or more network elements tocommunicate and receive data in connection with a video communicationsession. Indeed, a transmitting module 148 a, 148 b, 148 c can be usedto collect and send video call data collected at the terminal forsharing with other participating terminals in a video communicationsession. Further, receiving modules 142 a, 142 b, 142 c can be used toreceive and prepare for rendering video call data collected at andreceived from other participating terminals in a video communicationsession.

Note that the term ‘endpoint’ is a broad term that encompassed terminals105 a-b, 108 a-b, 110 a-b and, further, can also include devices used toinitiate a communication, such as a switch, a console, a proprietaryendpoint, a telephone, a bridge, a computer, a personal digitalassistant (PDA), a laptop or electronic notebook, an i-Phone, an iPad, aGoogle Droid, any other type of smartphone, or any other device,component, element, or object capable of initiating, joining, orotherwise participating in voice, audio, or data exchanges withincommunication system 100. Endpoint terminals 105 a-b, 108 a-b, 110 a-bcan further provide a user interface and input devices for use by an enduser within a video or multimedia communication session, such as amicrophone, a display, a keyboard, touchpad, mouse, cameras, or otherterminal equipment.

Video communication servers 125 a-b, 128 a-b can be configured toestablish, maintain, and otherwise manage a video session between one ormore terminal devices 105 a-b, 108 a-b, 110 a-b utilized by end userswho may be, in some instances, located in various remote sites andlocations. Video communication servers 125 a-b, 128 a-b can includerespective processors 152 a, 152 b, respective memory elements 154 a,154 b, and respective conference control modules 155 a, 155 b, which canbe used, among other functions, to control what images, user interfaceelements, video, and sound are exchanged, rendered, and presented on agiven terminal display for end users during a video session. In general,video communication servers 125 a-b, 128 a-b may communicate withendpoints (e.g., 105 a-b, 108 a-b, 110 a-b) through any suitablestandard or proprietary communication or conference control protocol. Insome instances, a video communication server (e.g., 125 a-b, 128 a-b)can further include a switching component that determines which signalsare to be routed to individual endpoints (e.g., 105 a-b, 108 a-b, 110a-b).

Video communication servers (e.g., 125 a-b, 128 a-b) can also determinehow individual end users are seen by others involved in the videoconference based on control elements, preset either by a videocommunication service provider or individual user, or dynamicallyspecified by participants during a video communication session.Additionally, video communication servers (e.g., 125 a-b, 128 a-b) cancontrol the timing and coordination of video communication sessionactivities, including the presentation of video call data on variousterminal endpoints participating in the session. Video communicationservers 125 a-b, 128 a-b can also coordinate and control videocommunication services and sessions according to particular policies,including user-specific and endpoint-specific policies that can be used,among other objectives, to customize or otherwise tailor functions, userinterfaces, and rights of an endpoint or user within a videocommunication session. For instance, in some examples, the ability toscreen video calls through a video preview of the caller can be offeredin accordance with a policy subscribed or agreed to by a particularuser.

Video communication sessions can make use of a variety of differentcomputing networks and network configurations. For instance, network 130can represent a series of points or nodes of interconnectedcommunication paths for receiving and transmitting packets ofinformation propagating between components in communication system 100.Network 130 can offers a communicative interface between the endpointterminals and other network elements (e.g., video communication server125 a-b, 128 a-b), and can be or include any local area network (LAN),intranet, extranet, wireless local area network (WLAN), metropolitanarea network (MAN), wide area network (WAN), virtual private network(VPN), the Internet, or any other appropriate architecture or systemthat facilitates communications in a network environment. In someinstances, network 130 can implement a UDP/IP connection and use aTCP/IP communication protocol in particular embodiments of the presentdisclosure. In other instances, network 130 can implement other suitablecommunication protocols for transmitting and receiving data packetswithin communication system 100.

Turning to the particular example shown in FIG. 2A, in addition toconference control modules 155 a, 155 b, video conference servers 125 a,125 b can further include a video preview module (e.g., 156 a, 156 b)configured to facilitate previewing of video data from an incoming call.The video preview module 156 a, 156 b can assist users receiving thecall in identifying the source of the incoming call thereby assistingthe user in determining whether the call should be answered or ignored.For instance, in one particular example, video preview module 156 a, 156b can identify a request or attempt by one terminal (e.g., 105 a) toinitiate a video call, video chat, or other video communication session,with another terminal (e.g., 110 a). The video preview module 156 a, 156b can identify that video previewing is enabled for the other terminal110 a and capture video data captured at the first terminal (e.g., 105a) while the user of the first terminal waits for the called terminal topick-up and join the video session. Unbeknownst to the user of the firstterminal (e.g., 105 a) captured video data can be provided to endpoint110 a for presentation on a display device of endpoint terminal 110 a,allowing the user of terminal 110 a to preview or screen the visualidentity of the caller and determine whether the user will agree toparticipate in the video session. Further, video preview module 156 a,156 b, in some implementations, can provide further functionalityincluding processing of a user's request to either ignore or join thevideo session in response to a received video preview, as well asperform particular actions (e.g., automatically blocking or warning theuser of subsequent calls from the same source, etc.) based on a user'sprevious response(s) to a preview.

As shown in the example of FIG. 2B, video previewing functionality canalso be realized, at least in part, at the endpoint terminal itself. Forinstance, in the example of FIG. 2B, each of endpoint terminals 105 b,108 b, 110 b further include a video preview module 134 a, 134 b, 135 cconfigured to facilitate the previewing of video data captured from acalling terminal prior to the called terminal joining the session andtransmitting video data. In some instances, functionality forfacilitating previewing of video data for use in screening incomingvideo calls, can be provided by modules (e.g., 134 a, 134 b, 135 c, 156a, 156 b) operating cooperatively at each of the endpoint terminal andvideo communication server.

It is to be understood that the examples shown and described in FIGS.2A-2B are simplified, non-limiting examples, presented solely togenerally illustrate certain concepts, features, and examples. It shouldbe further understood that while the examples of FIGS, 2A-2B showmultiple video communication servers 125 a-b, 128 a-b, in someimplementations, a single video communication server can be provided, incommunication with two or more terminals in a communication session andfacilitating video session management functions and video previewingfunctionality similar to that described above. Additionally, while insome instances, video communication servers can be located remotely fromvideo terminals and serve video session management functions to aplurality of different video terminals, in other instances, videocommunication servers can be implemented, in whole or in part, locallyat one or more video terminals, and can, in some instances, be dedicatedto managing, joining, and provisioning video communication sessions forone or more particular video terminals, among other implementations.

Turning to FIGS. 3A-3B, example representations are shown illustratingexample attempts to initiate video communication sessions in a systemincluding two or more video terminals (e.g., 105, 110) and one or morevideo communication servers (e.g., 125). In one example, a first user ofvideo terminal 105, attempts to engage another user, at terminal 110, ina video communication sessions, such as a video call, video chat, videoconference, or some other video communications session. A user interface305 (illustrated in very simplified form in the representations of FIGS.3A-3B) can be presented to the first user to assist the user inestablishing a video communication session with one or more otherterminals. For instance, an example user interface 305 can include userinterface (UI) elements allowing a user to specify the identity of theuser and/or terminal to be called or invited to the video communicationsession, as well as UI controls for confirming and initiating the call,defining particular policies, specifications, and settings for the videocommunication session, etc. Upon initiating or attempting to initiate avideo communication session with video terminal 110, data 310 can besent to a video communication server 125 managing the requested videocommunication session, such as a server or system providing videocommunication services to one or more different video terminals in asystem.

Upon receiving the first terminal's 105 attempt to initiate acommunication session with second terminal 110, video communicationserver 125 can, in some examples, prepare data 315 for use incommunicating the request to the second terminal 125, awakening andconfiguring the second terminal for participation in video communicationsessions, among other purposes and functions. For instance, in someexamples, video communication server 125 can provide the second videoterminal 110 with the opportunity to preview video data 318 captured orreceived by video communication server 125 prior to the second terminal110 joining the initiated session.

The initial video data 318 obtained from the calling terminal (e.g.,105) can be obtained using a variety of different techniques, sometechniques used or based, at least in part, according to the particulararchitecture or protocol applied in establishing the communicationsession with the participating terminals. For example, in someinstances, video data 318 can begin being transmitted by video terminalimmediately upon sending a video session initiation request (e.g., 310).In another example, after a video session initiation request (e.g., 310)is sent by terminal 105 and received by the video communication server125, video communication server 125 can indicate that a session has beeninitiated and request that video data 318 begin being transmitted fromterminal 105, terminating the session if an error or issue occurs injoining the called terminal (e.g., 110) to the session.

In still another example, in connection with initiating a video sessionrequested by terminal A, video communication server 125 can request thata video data sample be transmitted from terminal A in connection withthe authorization, acceptance, or optimization of the terminal's 105video data configuration for use within video sessions hosted or managedusing video communication server 125. In yet another example, inresponse to requesting the initiation of a video session, video terminal105 can establish an interface, such as an API or other interface, withvideo communication server 125 that allows video communication server toaccess, and in some instances, even control operation of videocollecting mechanisms at the terminal 105, allowing the videocommunication server to capture, in some cases covertly, video datadirectly from the terminal 105.

Preliminary video data 318 captured from cameras operating at terminal105 prior to the called terminal 110 joining the video session can beshared with terminal 110 as preview data, prior to terminal 110 joiningthe session. For instance, upon receiving a video call or invitation tojoin a video communication session, a user interface 320 can bepresented at terminal 110 that includes at least a portion of the videodata 318 captured at terminal 105. The video data 318 can include imagesof the caller(s) themselves, the location or setting of the caller, andother visual characteristics of the incoming call to assist the user ofthe receiving terminal 110 in identifying the source, context, orconditions of the call. In the simplified representation of userinterface 320 shown in FIG. 3A, a window 325 can be displayed thatincludes at least a portion of the captured video data 318. In someinstances, video data 318 can also include audio data captured atterminal 105, the captured audio data being presented along withcaptured video data in connection with user interface 320 at terminal110. Further, other data can also be presented at terminal 110 inaddition to preview video (e.g., 325), such as an identification of thesource of the call, including an affiliated telephone number or user IDassociated with the calling terminal 105, detected geographical locationof the call, etc., to thereby provide additional context to the user ofthe receiving terminal 110. Additionally, UI controls, such as controls330, 335, can also be provided, allowing the user of terminal 110 toprovide feedback in response to the received preview data.

For instance, UI controls 330, 335 can allow a user of terminal 110 toindicate whether the user wants to accept or deny the video call. OtherUI controls can also be provided, including controls for directing howthe preview data is displayed (e.g., how long the preview video datashould be presented, the portion of the user interface the preview videowindow 325 should occupy, whether to replay the captured preview videodata, etc.), controls for displaying additional data relating to thecalling terminal available to either the receiving terminal or videocommunication server 125, among other example UI controls.

In some example implementations, three or more terminals can participatein a video communication session, such as a video conference call,multi-way video chat session, multiway video call, etc. In someinstances, multiple terminals may have already joined or have beeninvited to join a particular video call or session to which a receivingterminal 110 has been invited. Accordingly, in such implementations,preview video data can include preview data collected from two or moredifferent terminals other than the receiving terminal. As in the exampleof a potential two-party call, a receiving terminal (e.g., 110)receiving an invitation to join a multi-party (e.g., three parties ormore) video session may similarly be interested in knowing the number ofparties involved in a video session as well as the identities of thoseparties. For instance, while a user may be comfortable with one or moreof the parties involved or invited to a multi-party call, including aprimary party or host of the session, the user may not be familiar withor trust other parties involved in the call. Accordingly, as in thetwo-party example shown in FIG. 3A, preview data can be collected from aplurality of video terminals and sent to one or more receiving terminalsinvited to participate in connection with a preview of the participantsinvolved in the session. For instance, a split screen view can bepresented in window 325, showing collected preview video data from aplurality of participant terminals in a multi-party session. In someinstances, some participants in the multi-party session may be invitedand not yet transmitting video data within a fully established session.Still, in some examples, preliminary video data can be captured ofparticipants invited to a multi-party session, including from terminalsthat have been invited but have not yet accepted and formally joined thevideo session, among other examples.

Preview video data presented to a user in connection with the screeningof an incoming video call or video communication session invitation, cantake many forms and formats. For instance, a single still image can becaptured from captured video data 318 and presented to the user ofterminal 110 in a user interface (e.g., 320) providing the preview tothe user. In other instances, a selected portion of collected video data318 can be presented as video in user interface 320. Select portions ofa collected video data 318, whether a video segment or still image, canbe automatically selected based on an identified relevance of the videoportion. For instance, a caller may temporarily exit the video framewhile waiting for the called terminal to join, making some preview videoless effective in alerting the called end user of the identity of thecaller. Accordingly, in order to maximize the chance that presentedpreview data is useful to the end user of the called terminal, selectportions can be selected, for instance, based on facial recognitionprocessing, identifying the presence of a human face within frames ofthe collected video data 318, identification of human voice directed toa microphone in proximity to the camera collecting video data 318(increasing the probability that the caller's face is within view of thecalling terminal's 105 camera), among other examples. In someimplementations, live video data 318 collected from the calling terminal105 can be displayed in a streaming or substantially live fashion onvideo terminal 110, for instance, based on the assumption that as thecall grows closer to connecting, the caller is most likely to be inposition (i.e., in front of terminal's 105 camera) for the start of thecall. In other instances, both a live feed of terminal 105 and selectedvideo segment can be presented (e.g., in split-screen view) to the userof the called terminal as preview video data. In additionalimplementations, the user of the called terminal can be presented withUI controls and corresponding functionality for replaying, slow-playing,freezing, and zoomed-in viewing of the preview data, to assist the userin analyzing the preview video data, among other examples.

In some instances, the presentation of preview video data at thereceiving terminal 110 can be optional or based on particularconditions. In some instances, a user may not wish to bother withadditional previewing steps in connection with joining a video sessionwith an expected or recognized caller. For instance, other data, such astraditional caller ID data (i.e., a name and phone number associatedwith a particular telephonic endpoint) associated with the callingterminal 105 can be displayed at the receiving terminal 110 along withUI controls that permit the user to elect to have preview video datacollected and/or displayed from the calling terminal 105 (e.g., when theuser of terminal 110 does not immediately recognize the identity of thecalling terminal 105 from other data or cues initially available to theuser). For instance, a user of the receiving terminal can be presentedwith an option to launch user interface 320 in response to receiving avideo call or other invitation to join a video communication session,allowing the user to optionally view preview data collected at thecalling terminal 105, among other examples.

Additionally, presentation of preview video data, such as in userinterface 320, can be conditioned upon certain criteria, events, orother aspects. For example, availability of video previewing features,such as described herein, can be offered as a paid subscription service,and presentation of user interface 320 and preview video data can beconditioned on the terminal 110, or a user account associated with theterminal, being authorized to consume this service and feature. In otherinstances, video previewing and call screening can be conditioned on theidentification, by the terminal 110 and/or video communication server125, that a particular video call or session originates from an unknownor otherwise unfamiliar caller. For instance, a listing of favorite,trusted, whitelisted, or otherwise known callers and terminals can bemaintained by the terminal 110 (or by video communication server 125 onbehalf of terminal 110 and other terminals), so that video sessionsinitiated by such callers and terminals do not automatically triggervideo screening of the call. Accordingly, calls from unknown,unfamiliar, or untrusted sources can, in some instances, automaticallytrigger the launch of video previewing of a call (e.g., using userinterface 320). Other factors and data can also be considered tointelligently drive when and how (e.g., automatically or optionally)video previewing is launched by the terminal 110 and/or videocommunication server 125, including the time of day the call arrives,the geographic source of the call, whether the call originates from anoutside video communication service or out-of-network caller, etc.,among other considerations.

Continuing with the example of FIG. 3A, following the presentation ofpreview video data 318, a user at terminal 110 can indicate whether theuser wishes to accept the call, thereby resulting in data 350 being sentindicating whether the user of terminal 110 accepts the call or not. Inthe example of FIG. 3A, data 350 indicates that the user of terminal 110has agreed to accept the video call from terminal 105, and a videocommunication session is established between terminals 105 and 100, withvideo call data 355 being exchanged by both terminals 105, 110 withinthe session.

It should be noted that, in this example, prior to receiving a user'sresponse to preview video data (i.e., indicating whether a video callwill be accepted or not), video data collected at terminal 110 is notshared with the calling terminal 105, thereby preserving the privacy andconcealing the intentions and availability of the user of terminal 110from the user of terminal 110. However, once authorization is received(e.g., at 350), video data is collected from terminal 110 and sharedwith the calling terminal 105 as is typical in video-enabledcommunication sessions. Accordingly, video data showing the user of thecalled terminal 110 is displayed 360 at the calling terminal 105, whilevideo showing the user of the calling terminal 105 is displayed 365 atthe called terminal 110.

While in the example of FIG. 3A, a user of the called terminal (e.g.,110) elected to join a video session after receiving and evaluatingreceived preview video data, in some instances, the user may elect notto join the session, based, for instance, on an evaluation of thereceived preview data. In instances where preview video data has beenpresented to the user of the called terminal (e.g., 110), and the userof the called terminal has elected not to join the video communicationsession, data 370 communicating the user's decision can be collected ata user interface (e.g., 320) of the called terminal and sent to videocommunication server 125.

Based on the response data 370, video communication server can act tocommunicate that the called terminal did not join the video sessionwhile, in some instances, hiding the fact that a video preview of datacollected from calling terminal 105 was presented at terminal 110potentially causing the called terminal 110 not to join the call.Tactfully handling a denial to join a call by a called terminal can beimportant from a user experience perspective, as the user of the calledterminal may want to guard against potentially offending the deniedcaller (e.g., when the user intends to call-back the denied caller at amore convenient time, etc.).

For instance, data 375 can be prepared by video communication server 125to generically communicate that the video communication server 125failed to establish a session with the called terminal 110. In someinstances, data 375 can communicate the failure to establish a sessionwhile remaining silent regarding the presentation of collected previewdata 318 at the called terminal 110. Indeed, in some instances, data 375received at the calling terminal 105 can be rendered by calling terminalto cause a user interface 380 to be displayed to the caller thatintimates that the failure to connect to the called terminal 110 wastechnical in nature (e.g., as a result of a network error, failure ofthe called terminal 110 to respond, etc.). Accordingly, user interface380 can include an option to allow the caller to retry connecting to theoriginally called video terminal 110 (e.g., using UI control 390).

Upon declining a video session invitation or video call, the calledterminal 110 can also present one or more user interfaces 385 to thecalled user providing the user with options for performing actionspertaining to the user's decision to deny (or even accept) a receivedvideo session invitation. For instance, a user, in connection withdenying or accepting a video call from a particular terminal device oruser associated with the terminal (e.g., through an associated useraccount), can elect to blacklist or whitelist the caller so as toautomatically deny or block future calls in the case of a blacklist orautomatically connect to futures calls from callers included in awhitelist. In some instances, data can be captured from the previewvideo data for use in identifying, from future received video data, thata blacklisted (or whitelisted) caller is attempting to contact theterminal or user associated with the blacklist.

In some instances, a particular person can attempt to contact a user orterminal using a variety of user accounts, aliases, and terminaldevices. Rather than blocking future calls from a blacklisted caller (orautomatically joining calls from a whitelisted caller) characteristicsof subsequent video data can be analyzed for similarities withpreviously collected preview video data associated with a user'sdecision to blacklist (or whitelist) a particular caller or party. Forinstance, face data can be captured from the preview video data,associated with the blacklisted caller, and stored as reference data toidentify the blacklisted caller in future video communication sessions,for instance, based on facial recognition analysis of the future videostream (such as in future preview video data).

Other implementations can capture reference data corresponding to uniquebackground features included in preview video data (e.g., presented inconnection with a blacklisting (or whitelisting) of a particular user,such as the layout of a room, architectural features, furniture, andother elements, including signage and multi-media data presented withina frame of preview video data associated with a blacklisted user). Suchfeatures can also be identified in connection with future videosessions, including preview video data sent to a receiving terminal inconnection with an invitation to the future video session, and comparedagainst stored reference data in order to identify a repeat blacklisted(or whitelisted) caller.

In some implementations, a user of a called terminal, upon reviewingpreview video data collected at a calling terminal, can elect, via UIcontrols presented in a user interface (e.g., 320, 385) of the calledterminal, to launch a report, for instance, of a terms of use violationor illegal act observed by the user in the presented preview video data.Further, the preview video data can be saved or stored and associatedwith the identified caller as evidence of the reported violation, thepreview video data being stored locally at the called, reportingterminal or in memory of a remote video communications server 125, etc.

In some instances, a user, rather than outright rejecting an invitationto join a video session, can elect to only partially join the videosession without transmitting video data from the called terminal (e.g.,110). For instance, in response to viewing preview video data, a user ofthe called terminal 110 can elect to partially join a videocommunication session so as only to allow voice data (and not videodata) to be collected for presentation to other participants in thevideo session. In some instances, such an election can cause acommunication (e.g., using data 375) to the calling terminal and otherparticipating terminals that only audio data is able to be presentedwithin the particular session, thereby hiding the reality that thecalled user has elected that video data not be shared with the otherparticipants, for example, because the called user has determined thatthey are uncomfortable with sharing video data with the otherparticipant(s) based on preview video data collected from the otherparticipant(s). In other implementations, such as in a video conferenceenvironment, the called user can partially join the meeting so as to“lurk” in the session, consuming video (and audio) data transmitted fromother participants while hiding the user's participation in the meetingfrom one or more other users and withholding video data from beingshared within the session.

It should be noted, that while the examples illustrated in FIGS. 3A-3B,show that terminal 110 is the receiving or called terminal in a videocommunication session and terminal 105 is the calling or initiatingterminal in the video communication session, in other examples, theroles of the respective terminals can be reversed. Terminals can bothsend and receive requests to join a video session, and any terminal in anetwork of terminals can be permitted to initiate a new video session.Further, in some instances, terminals can both screen incoming videocalls from other terminals (e.g., via preview video data) as well as bescreened by other terminals. For instance, terminal 110, in an alternateexample, could initiate a call with video terminal 105 prompting videoterminal 105 to screen, via preview video data collected from terminal110, the caller of terminal 110 to assist the user of terminal 105 indecided whether to join the session launched by terminal 110. As inother examples described above, when screening collected preview videodata, video data from the screening terminal 105 may be withheld fromthe screened terminal and the screened terminal may be unaware thatvideo data collected from the screened terminal is being screened orpreviewed by the screening terminal 105.

Turning to FIG. 4A, a simplified flowchart 400 a is shown of an exampletechnique for previewing an incoming video communication sessioninvitation. A request to join a video communication session can beidentified at 405. The request can take the form of an incoming videocall, incoming video chat request, invitation to join a videoconference, and other requests to join video communication sessions.Identifying such a request can include, among other examples, a videocommunication server receiving a request from a first terminal tofacilitate a video session between the first terminal and one or moreother terminals. Identifying a request for a called terminal to join avideo communication session can also include the calling terminalreceiving an invitation or other request to join the video communicationsession, either from a video communication server facilitating thesession or from the calling terminal directly, among other examples.

Upon identifying the incoming request, video data captured at the firstterminal requesting or originating the session, or other terminals alsoincluded in or invited to the session (i.e., preview video data), can beallowed (at 410) to be presented at a second, called terminal before thesecond terminal joins the session and shares video data with otherterminals that are to be included in the session. Allowing such previewvideo data to be presented at the second, called terminal can includecapturing video data from the other participant terminals, selectingvideo data from the captured video data for inclusion in the previewvideo data, and sending at least a portion of the captured video data tothe second, called terminal for presentation in a user interface of thesecond terminal.

One or more video communication servers or other devices and modules canbe used to capture and forward preview video data to a terminal. In someinstances, the second terminal can, for instance, via an API to thecalling terminal or a meeting or video chat client installed on thecalling terminal, capture preview video data from the calling terminaland have the captured data forwarded directly to the called terminal. Insome instances, video data from a calling or participating terminal canbe collected and/or previewed at the other receiving or called terminalwithout the user of the calling or participating terminals knowing thatsuch data has been shared with the called terminal prior to the videosession formally beginning.

Turning now to FIG. 4B, another simplified flowchart 400 b is shown ofan example technique for acting on received preview video data. Inresponse to presented preview video data on a called terminal, a request(e.g., via user input) can be received at 420: indicating that one ormore callers to whom the preview video data applied should be includedin one or more particular categories. For instance, a user can assignvarying preferences, profiles, and permissions to particular callers. Asexamples, a user can designate that certain callers be whitelisted orblacklisted. Some callers can be categorized as friends and family,others categorized as business relationships, while still otherscategorized as solicitors, among potentially countless other categories.A set of characteristics of the caller can be determined at 425 from thepreview video data. For instance, facial recognition can be performed onthe preview video data to identify face data corresponding to one ormore callers. The face data can be stored, for example, in a database orother data store, either locally or remotely, and associated with theparticular caller. Associating characteristics with a caller can includeassociating the characteristics (such as face data, a telephone number,video calling service, terminal, etc.) with a particular user or accountID, terminal identifier, or other identifier associated with the calleror terminal from which the caller attempted to reach the called party.

Future requests to have a terminal join a video communication sessioncan be identified at 430. Data included or associated with the requestcan be analyzed (such as video preview data, location information, or atelephone number corresponding to the future request, among otherexamples) to identify at 435 that at least one characteristic in the setof previously-identified characteristics is included in, or otherwisealso associated with the identified future request. For instance, facialrecognition can be performed on preview video data or other video datacollected in connection with the future request to determine at 440,based on corresponding stored face data, that the first caller is alsoinvolved in, or the source, of the subsequent request. The identity ofsubsequent callers can thus be automatically determined, based onfeedback received and data collected in connection with video sessionpreviews corresponding to earlier video communication sessions andattempts.

Further, based on a user's request to categorize a particular caller,automatic identification (e.g., at 440) of the caller in connection withsubsequent video sessions can trigger automated responses to thecaller's subsequent calls. For instance, a blacklisted caller can beautomatically identified and blocked, saving the called user from havingto re-assess calls from such unwanted callers. Further, a called usercan be alerted to particular calls based on the identity and/or categoryof the caller. As an example, video session requests from callersdetermined to have a particular identity, and thus included within aparticular category, can cause the called terminal to provide certainalerts to the user (such as different ringtones or graphical displays)based on the caller's determined identity or corresponding categories.

Although this disclosure has been described in terms of certainimplementations and generally associated methods, alterations andpermutations of these implementations and methods will be apparent tothose skilled in the art. For example, the actions described herein canbe performed in a different order than as described and still achievethe desirable results. As one example, the processes depicted in theaccompanying figures do not necessarily require the particular ordershown, or sequential order, to achieve the desired results. In certainimplementations, multitasking and parallel processing may beadvantageous. Additionally, other user interface layouts andfunctionality can be supported. Other variations are within the scope ofthe following claims.

Embodiments of the subject matter and the operations described in thisspecification can be implemented in digital electronic circuitry, or incomputer software, firmware, or hardware, including the structuresdisclosed in this specification and their structural equivalents, or incombinations of one or more of them. Embodiments of the subject matterdescribed in this specification can be implemented as one or morecomputer programs, (i.e., one or more modules of computer programinstructions, encoded on computer storage medium for execution by, or tocontrol the operation of, a data processing apparatus). Alternatively orin addition, the program instructions can be encoded on an artificiallygenerated propagated signal, e.g., a machine-generated electrical,optical, or electromagnetic signal that is generated to encodeinformation for transmission to suitable receiver apparatus forexecution by a data processing apparatus. A computer storage medium canbe, or be included in, a computer-readable storage device, acomputer-readable storage substrate, a random or serial access memoryarray or device, or a combination of one or more of them.

Moreover, while a computer storage medium is not a propagated signal, acomputer storage medium can be a source or destination of computerprogram instructions encoded in an artificially generated propagatedsignal. The computer storage medium can also be, or be included in, oneor more separate physical components or media (e.g., multiple CDs,disks, or other storage devices), including a distributed softwareenvironment or cloud computing environment.

The operations described in this specification can be implemented asoperations performed by a data processing apparatus on data stored onone or more computer-readable storage devices or received from othersources. The terms “data processing apparatus,” “processor,” “processingdevice,” and “computing device” can encompass all kinds of apparatus,devices, and machines for processing data, including by way of example aprogrammable processor, a computer, a system on a chip, or multipleones, or combinations, of the foregoing. The apparatus can includegeneral or special purpose logic circuitry, e.g., a central processingunit (CPU), a blade, an application specific integrated circuit (ASIC),or a field-programmable gate array (FPGA), among other suitable options.While some processors and computing devices have been described and/orillustrated as a single processor, multiple processors may be usedaccording to the particular needs of the associated server. Referencesto a single processor are meant to include multiple processors whereapplicable. Generally, the processor executes instructions andmanipulates data to perform certain operations. An apparatus can alsoinclude, in addition to hardware, code that creates an executionenvironment for the computer program in question, e.g., code thatconstitutes processor firmware, a protocol stack, a database managementsystem, an operating system, a cross-platform runtime environment, avirtual machine, or a combination of one or more of them. The apparatusand execution environment can realize various different computing modelinfrastructures, such as web services, distributed computing and gridcomputing infrastructures.

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read only memory ora random access memory or both. The essential elements of a computer area processor for performing actions in accordance with instructions andone or more memory devices for storing instructions and data. Generally,a computer will also include, or be operatively coupled to receive datafrom or transfer data to, or both, one or more mass storage devices forstoring data, e.g., magnetic, magneto optical disks, or optical disks.However, a computer need not have such devices. Moreover, a computer canbe embedded in another device, e.g., a mobile telephone, a personaldigital assistant (PDA), tablet computer, a mobile audio or videoplayer, a game console, a Global Positioning System (GPS) receiver, or aportable storage device (e.g., a universal serial bus (USB) flashdrive), to name just a few. Devices suitable for storing computerprogram instructions and data include all forms of non-volatile memory,media and memory devices, including by way of example semiconductormemory devices, e.g., EPROM, EEPROM, and flash memory devices; magneticdisks, e.g., internal hard disks or removable disks; magneto opticaldisks; and CD ROM and DVD-ROM disks. The processor and the memory can besupplemented by, or incorporated in, special purpose logic circuitry.

In more general terms, video communication server 125 is a networkelement that can be provisioned in virtually any communicationsarchitecture, system, network, etc. Moreover, such a network element(i.e., video communication server 125) has considerable breadth and,therefore, necessarily encompasses various types of routers, switches,gateways, bridges, loadbalancers, firewalls, servers, inline servicenodes, proxies, processors, modules, nodes, or any other suitabledevice, component, element, or object operable to exchange informationin a network environment. The network element may include appropriateprocessors, memory elements, hardware and/or software to support (orotherwise execute) the activities associated with using a processor forscreen management functionalities, as outlined herein. This includes thememory elements being able to store code (e.g., software, logic,processor instructions, etc.), that can be executed to carry out theactivities described herein. Moreover, the network element may includeany suitable components, modules, interfaces, or objects that facilitatethe operations discussed herein with reference to managing video data.This may be inclusive of appropriate algorithms and communicationprotocols that allow for the effective exchange of data or informationin the network.

To provide for interaction with a user, embodiments of the subjectmatter described in this specification can be implemented on a computerhaving a display device, e.g., a CRT (cathode ray tube) or LCD (liquidcrystal display) monitor, for displaying information to the user and akeyboard and a pointing device, e.g., a mouse or a trackball, by whichthe user can provide input to the computer. Other kinds of devices canbe used to provide for interaction with a user as well; for example,feedback provided to the user can be any form of sensory feedback, e.g.,visual feedback, auditory feedback, or tactile feedback; and input fromthe user can be received in any form, including acoustic, speech, ortactile input. In addition, a computer can interact with a user bysending documents to and receiving documents from a device, includingremote devices, that are used by the user.

Although the present disclosure has been described in detail withreference to particular embodiments, it should be understood thatvarious other changes, substitutions, and alterations may be made heretowithout departing from the spirit and scope of the present disclosure.For example, although the present disclosure has been described asoperating in conferencing environments or arrangements, the presentdisclosure may be used in any communications environment that couldbenefit from such technology. Virtually any configuration that seeks tointelligently offer a preview of video data (or of individuals) couldenjoy the benefits of the present disclosure. The can readily includeSkype™ applications, web cam architectures, WebEx™ platforms,MeetingPlace™ platforms, Google Chat™, or any other architecture orplatform configured for exchanging data.

In addition, it should be noted that certain users may have their videodata blocked such that some of the objectives discussed herein may befrustrated. For example, some endpoints may include privacy settings (orservice provider settings) that preclude caller ID from being viewed.This may include indicators that display ‘private’ for inbound callsassociated with an originating caller. A similar paradigm can bedeployed in the context of the present disclosure, where a user may haveprovisioned privacy setting for which an attempt to retrieve video datamay not be possible. In such instances, a simple message can be sent tothe counterparty to relay that this video data cannot be displayed priorto a second endpoint electing to join a video communication session.

Numerous other changes, substitutions, variations, alterations, andmodifications may be ascertained to one skilled in the art and it isintended that the present disclosure encompass all such changes,substitutions, variations, alterations, and modifications as fallingwithin the scope of the appended claims. In order to assist the UnitedStates Patent and Trademark Office (USPTO) and, additionally, anyreaders of any patent issued on this application in interpreting theclaims appended hereto, Applicant wishes to note that the Applicant: (a)does not intend any of the appended claims to invoke paragraph six (6)of 35 U.S.C. section 112 as it exists on the date of the filing hereofunless the words “means for” or “step for” are specifically used in theparticular claims; and (b) does not intend, by any statement in thespecification, to limit this disclosure in any way that is not otherwisereflected in the appended claims.

What is claimed is:
 1. A method, comprising: identifying a request, froma first endpoint, for a second endpoint to join a video communicationsession between the first endpoint and a third endpoint; allowingparticular video data captured at the first endpoint and the thirdendpoint to be displayed concurrently at the second endpoint prior tothe second endpoint joining the video communication session; identifyingthat the particular video data includes presentation of a human facebefore allowing the particular video data to be presented on the secondendpoint, wherein the identifying is performed without humanintervention; and identifying a confirmation from the second endpoint tojoin the video communication session following a display of theparticular video data on the second endpoint; wherein the first endpointis not made aware that the particular video data is displayed at thesecond endpoint prior to the second endpoint joining the videocommunication session.
 2. The method of claim 1, wherein the particularvideo data is displayed as video data on the second endpoint.
 3. Themethod of claim 1, wherein the particular video data is displayed on thesecond endpoint as a still image.
 4. The method of claim 1, furthercomprising: identifying a presentation of a human face in the particularvideo data; and associating face data corresponding to the presentedhuman face with a video caller using the first endpoint.
 5. The methodof claim 4, further comprising: identifying a response, received at thesecond endpoint, indicating whether the video communication session withthe video caller is desired.
 6. The method of claim 5, furthercomprising: identifying that a second request to join a second videocommunication session includes the video caller based on a facialrecognition of preliminary video data, wherein the facial recognitionincludes a comparison of at least a portion of the preliminary videodata with the face data.
 7. The method of claim 1, further comprising:identifying a denial from the second endpoint declining to join thevideo communication session following a display of the particular videodata on the second endpoint.
 8. The method of claim 6, furthercomprising: identifying a response, received at the second endpoint,indicating whether a video communication session with first endpoint isdesired; and performing an action corresponding to the second requestbased on the response.
 9. The method of claim 8, wherein the actionincludes associating the identified response with an identifiercorresponding to the first endpoint.
 10. The method of claim 9, furthercomprising: identifying that a second request to join a second videocommunication session includes an endpoint associated with theidentifier; and generating a response to the second request.
 11. Themethod of claim 8, wherein the action includes a selected one of a groupof actions, the group consisting of: a) blocking the second request; b)causing an endpoint other than the endpoint associated with theidentifier to join the second video communication session; c) presentinga notification that the second request is associated with theidentifier, reporting the second request; d) joining the second videocommunication as an audio participant only; and e) joining the secondvideo communication session anonymously without sharing video datawithin the session.
 12. The method of claim 1, wherein identifying therequest from the first endpoint and allowing the particular video datato be displayed at the second endpoint is performed by a video callserver used to establish video communication sessions between the secondendpoint and at least one other endpoint.
 13. The method of claim 1,wherein the request from the first endpoint is identified by the secondendpoint and the second endpoint allows the particular video data to bedisplayed at the second endpoint prior to the second endpoint joiningthe video communication session.
 14. Logic encoded in non-transitorymedia that includes code for execution and when executed by a processoris operable to perform operations, comprising: identifying a request,from a first endpoint, for a second endpoint to join a videocommunication session between the first endpoint and a third endpoint;allowing particular video data captured at the first endpoint and thethird endpoint to be displayed concurrently at the second endpoint priorto the second endpoint joining the video communication session;identifying that the particular video data includes presentation of ahuman face before allowing the particular video data to be presented onthe second endpoint, wherein the identifying is performed without humanintervention; and identifying a confirmation from the second endpoint tojoin the video communication session following a display of theparticular video data on the second endpoint; wherein the first endpointis not made aware that the particular video data is displayed at thesecond endpoint prior to the second endpoint joining the videocommunication session.
 15. An apparatus, comprising: a processor; amemory element; and a video preview module, the apparatus beingconfigured to: identify a request, from a first endpoint, for a secondendpoint to join a video communication session between the firstendpoint and a third endpoint; allow particular video data captured atthe first endpoint and the third endpoint to be displayed concurrentlyat the second endpoint prior to the second endpoint joining the videocommunication session; identify that the particular video data includespresentation of a human face before allowing the particular video datato be presented on the second endpoint, wherein the identifying isperformed without human intervention; and identify a confirmation fromthe second endpoint to join the video communication session following adisplay of the particular video data on the second endpoint; wherein thefirst endpoint is not made aware that the particular video data isdisplayed at the second endpoint prior to the second endpoint joiningthe video communication session.
 16. The apparatus of claim 15, furthercomprising: a video call server configured to establish videocommunication sessions between the second endpoint and at least oneother endpoint, wherein the video call server includes the video previewmodule.
 17. The apparatus of claim 15, wherein the second endpointincludes the video preview module.